Some weeks ago I switched from Stratux to the SkyEcho 2. So far it works very well in combination with SkyDemon. I use the SkyEcho 2 only as receiver for ADS-B and FLARM. And I am not always flying the same aircraft and so I can't store the FLARM and ADS-B hex code in the SkyEcho 2 or I would have to adjust both frequently (see post "SkyEcho Set Aircraft Reg and Hex Code from Skydemon"). So it happens that at the beginning of a flight I hear permanent traffic warnings (ghost plane) - which can be very "stressful" (see post "Suppress traffic warnings below a certain height"). I know that I can ignore a aircraft (with one touch on the Traffic Radar). But on ground I often can't decide which aircraft should be ignored.

Before the SkyEcho 2 I had a Stratux in use. And back then I had no problems with a "ghost plane" (not even when changing the aircraft). In the SkyDemon "Aircraft Profile" I had always stored the FLARM HEX ID. But the SkyEcho 2 doesn't seem to transmit a FLARM HEX ID to SkyDemon when Flarm is used (received). You see only the text "FLARM" in the Traffic Radar. This seems to be the difference between Stratux and SkyEcho 2.

Can this be fixed?

Sorry for my english. Let me try to describe it in more detail. First of all, it is important to know that there are a lot of gliders active at our site. And they all have a FLARM on board. The powered aircraft also have FLARM installed (and ADS-B or MODE-S). I myself fly with two different TMGs (with installed FLARM + ADS-B or Mode-S).

2018/2019 I started to use a "Stratux" in combination with SkyDemon. And was very satisfied with the integration of the traffic warnings. In the beginning I also had the "ghost" problem there. But like you said before, I was able to solve this quickly and easily using the FLARM HEX ID in the aircraft profile. A few weeks ago I switched to the SkyEcho 2 (for various reasons). And the ghost problem was there again. In the beginning I thought I had gotten the wrong profile in planning. But soon it was clear that it was not the profile. Also the HEX ID of the FLARM transmitters remained unchanged. So I continued to search for the cause. My guess is that the SkyEcho 2 does not "send" the FLARM ID to the SkyDemon. When I touch on the Traffic Radar and have a look at the list, I only see list items with the entry "FLARM" and the distance (in the next line). If there is an ADS-B target around me, I see the callsign and the distance. And I seem to remember that in the past (= Stratux) FLARM targets also showed the HEX ID in the list. I hope that I have now described it a bit more understandable.

SkyEcho 2 itself has the posibility to filter one ADS-B ID and one FLARM ID. But that means that it has to be adjusted every time the aircraft is changed.

Currently I do not know when I can fly again (lockdown). But I could compare both systems again at the airfield - if that helps.